<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
<HEAD>

<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2016. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<TITLE>
Building a Rich Client Platform application
</TITLE>

<link rel="stylesheet" type="text/css" HREF="../book.css">
</HEAD>
<BODY BGCOLOR="#ffffff">
<h1>Building a Rich Client Platform application</h1>
<p>
While the Eclipse platform is designed to serve as an open tools platform, it is architected so that its components could be 
used to build just about any client application.  The minimal set of plug-ins needed to build a rich client application is collectively
known as the <b>Rich Client Platform</b>.  
</p>
<p>
Applications that don't require a common resource model can be built using a subset of the platform.  These rich applications
are still based on a dynamic plug-in model, and the UI is built using the same toolkits and extension points. 
</p>

<p>
Eclipse RCP applications are defined to use dependency injection and a service orientated architecture. The Eclipse renderer
framework allow to control the appearance of the default user interface and clients can use either the default renderer for SWT or 
custom renderers for other UI technologies. The Eclipse platform provides the E4Application as default entry point but clients are free to create their own application.
</p>
<p>
Rich client applications are free to use any API deemed necessary 
for their feature set, and can require any plug-ins above the bare minimum.  The 
<a href="../reference/misc/overview-platform.html">Map of platform plug-ins</a> is a useful 
reference when determining what plug-ins should be required when using various platform
API.
</p>


</BODY></HTML>